Using Tokenize

The Tokenize request provides an option to return a multi-use token without card issuer verification.  If the Tokenize request contains bad data (for example, an invalid card number), when the Token is used in transaction processing, it will return an error.  This risk is assumed by the merchant if they choose to use Tokenize instead of requesting a token for an approved credit transaction.

When data is tokenized, it includes both the PAN and the expiration date.

During Credit Transaction Processing

When a merchant requests that a token be returned, the associated transaction (auth, sale, reversal, etc.) is processed before requesting a token. The transaction response is always returned to the merchant POS.

If the associated transaction response is a non-approval, the token request is not processed. This is indicated in the TokenRspCode returned in the response to the client POS.

If the transaction is approved by the card issuer with a response of APPROVAL, PARTIAL APPROVAL, or CARD OK, a token is requested from the tokenization service and a TokenData response block is returned to the merchant POS. The TokenData response block may include the generated token in the TokenValue field depending on the success or failure of the tokenization request.

When data is tokenized, it includes both the PAN and expiration date.